Designing Before Coding

$npx mdskill add obra/clank/Designing Before Coding

Structure complex logic by first drafting pseudocode, iterating on approaches before writing any implementation.

  • Prevents writing messy, incomplete code by forcing upfront architectural planning.
  • Requires no external tools; it is a pure process enhancement for logic development.
  • Activates when the task complexity exceeds simple, immediate coding efforts.
  • Delivers a structured, multi-stage plan, moving from abstract concepts to concrete syntax.

SKILL.md

.github/skills/Designing Before CodingView on GitHub ↗

No skill content available yet.

More from obra/clank

SkillDescription
Commenting IntentComment WHY code exists and non-obvious decisions, not WHAT code does (mechanics)
Creating SkillsTDD for process documentation - test with subagents before writing, iterate until bulletproof
Domain-Focused NamingName code by what it does in the domain, not how it's implemented or its history
Encapsulating ComplexityHide implementation details behind interfaces - work at domain level (what), not implementation level (how)
Exploring AlternativesTry 2-3 different approaches before implementing - don't settle for first design you think of
Installing Skills SystemFork, clone to ~/.clank, run installer, edit CLAUDE.md
Keeping Routines FocusedEach routine does one thing and does it well - extract when routines have multiple responsibilities
Localizing VariablesDeclare variables in smallest possible scope, initialize close to first use, minimize span and live time
Maintaining Consistent AbstractionsClass interfaces present one cohesive abstraction - don't mix domain logic with serialization, persistence, or unrelated concerns
Naming VariablesChoose names that fully and accurately describe what the variable represents